Virtualized radio access network architecture for applications requiring a time sensitive network

ABSTRACT

Techniques associated with localizing data traffic for a time sensitive network within a virtualized radio access network are provided. In one embodiment, a method includes determining that a user equipment (UE) is associated with a time sensitive network; and localizing data traffic for the UE within a virtualized radio access network based on determining that the data traffic for the UE can be localized at one centralized user plane component of the virtualized radio access network for the time sensitive network. The data traffic can be Layer-2 data traffic or unstructured data traffic.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of priority under 35 U.S.C. § 119 toU.S. Provisional Patent Application Ser. No. 62/820,925, entitled“VIRTUALIZED RADIO ACCESS NETWORK ARCHITECTURE FOR APPLICATIONSREQUIRING A TIME SENSITIVE NETWORK,” filed on Mar. 20, 2019, thedisclosure of which application is hereby incorporated by reference inits entirety.

TECHNICAL FIELD

The present disclosure relates to mobile wireless network equipment andservices.

BACKGROUND

Fifth Generation (5G) networks have use cases that need to providesupport for Time Sensitive Networks (TSNs). A virtualized Radio AccessNetwork (vRAN) architecture is not aware of TSN requirements.Accordingly, there are significant challenges in supporting TSNs forvRAN architectures.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system depicting a virtualized RadioAccess Network (vRAN) in which techniques for providing an optimizeddata path for a Time Sensitive Network (TSN) may be implemented,according to an example embodiment.

FIGS. 2A-2B are block diagrams depicting optimized data paths for thesystem of FIG. 1 for various example scenarios, according to an exampleembodiment.

FIG. 3 is a message sequence diagram illustrating a call flow forfacilitating a TSN bridge within the vRAN to provide an optimized datapath that is localized within the vRAN, according to an exampleembodiment.

FIG. 4 is a message sequence diagram illustrating a call flow forfacilitating usage reporting for user equipment data traffic associatedwith a TSN, according to an example embodiment.

FIG. 5 is a flow chart depicting a method according to an exampleembodiment.

FIG. 6 is a hardware block diagram of a computing device that mayperform functions described herein in connection with the techniquesdepicted in FIGS. 1-5, according to an example embodiment.

DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

Presented herein are techniques to leverage a virtualized Radio AccessNetwork (vRAN) split architecture to set-up a Time Sensitive Network(TSN) that is geographically localized in the coverage area of a singleor a small set of next generation NodeBs (gNBs). In at least oneembodiment, provided herein is a system and method to provide anoptimized data path localized within the vRAN for a TSN session in orderto reduce latency and jitter for the TSN session.

A computer-implemented method is provided in one example embodiment andmay include determining that a user equipment (UE) is associated with atime sensitive network; and localizing data traffic for the UE within avirtualized radio access network based on determining that the datatraffic for the UE can be localized at one centralized user planecomponent of the virtualized radio access network for the time sensitivenetwork. The data traffic can be Layer-2 data traffic or unstructureddata traffic.

EXAMPLE EMBODIMENTS

Discussed herein are features associated with RAN architectures. In someinstances, a RAN architecture can be implemented as a centralized(disaggregated) RAN architecture that includes the split of a basestation, such as a gNB, into a Central (or Centralized) Unit (CU) andone or several Distributed Units (DUs). Further disaggregation mayinclude separation of the CU into a Centralized Unit Control Plane(CU-CP) component and a Centralized Unit User Plane (CU-UP) component.

Further, a RAN architecture can be virtualized in which hardware,software, and networking resources of one or more compute nodes can beabstracted to provide functionality for RAN nodes in order to implementa vRAN architecture in which functionality for the CU (and itsdisaggregated components, if applicable) can be implemented as avirtualized CU (vCU, including disaggregation into a vCU-CP andvCU-UP(s)) and functionality for the DUs can be implemented asvirtualized DUs (vDUs).

Networks such as 3rd Generation Partnership Project (3GPP) 5G networkshave use cases that need to provide mechanisms for Layer-2 (L2) EthernetPacket Data Unit (PDU) or unstructured PDU (e.g., non-Internet Protocol(IP) PDU) support, specifically for Time Sensitive Networks (TSNs).Generally, a TSN involves time-sensitive transmissions.

Applications that may require a TSN may include a wide variety ofapplications such as Internet of Things (IoT) applications, industrialautomation applications, enterprise applications, or any otherapplications that involving time-sensitive transmissions that may havestringent requirements for packet loss, network latency, and jitter. Ingeneral, latency can be impacted by the transmission and processing ofdata packets while jitter can be impacted by the number of nodes or“hops” that data packets traverse during communications and also howmuch data buffering is allowed by end applications.

Normally, a vRAN is not aware of any such TSN requirements because whena user equipment (UE) initiates attach procedures vRAN components suchas a virtualized Distributed Unit (vDU) and a virtualized Central Unit(vCU) forward the messages to an Access and Mobility Management Function(AMF) and after all control plane signaling is completed successfully anappropriate Packet Data Network (PDN) session is set-up in User PlaneForwarding (UPF) and session management information is stored andmaintained in Session Management Function (SMF) to support a TSN.

Presented herein are techniques to leverage a vRAN split architecture(vCU, vDU) and set-up a TSN that is geographically localized in thecoverage area of a single or a small set of next generation NodeBs(gNBs). In particular, embodiments herein provide a system and method toprovide an optimized data path that is localized within the vRAN for aTSN session of a UE in order to reduce latency and jitter for the TSNsession.

FIG. 1 is a block diagram of a system 100 depicting a virtualized RadioAccess Network (vRAN) 110 in which techniques for providing an optimizeddata path for a Time Sensitive Network (TSN) 120 may be implemented,according to an example embodiment. The system 100 includes nodes suchas a vCU-CP 112, vCU-UPs 114(1)-114(2), and vDUs 116(1)-116(2) for avRAN 110. A TSN 120 and user equipment (UEs) 122(1)-122(2) are alsoshown in system 100. System 100 also includes nodes such as a User PlaneFunction (UPF) 130, an Access and Mobility Management Function (AMF)132, a Session Management Function (SMF) 134, a Unified Data Management(UDM) 136, a Policy Control Function (PCF) 138, a Charging Function(CHF) 140, and a network 142.

Various 3GPP interfaces, sometimes referred to as reference points,facilitate communications/interactions among various elements of system100. Each vDU 116(1)-116(2) interfaces with an antenna assembly118(1)-118(2) that include transmitter and receiver hardware to enablewireless radio frequency communication via antennas with UEs 122. EachvCU-UP 114(1)-114(2) may interface with both vDUs 116(1)-116(2) viacorresponding F1-U interfaces in which the vDUs 116(1)-116(2) andvCU-UPs 114(1)-114(2) facilitate user plane communications (e.g., userdata traffic) for user data paths associated with TSN 120, discussed infurther detail herein.

Each vCU-UP 114(1)-114(2) may further interface with UPF 130 viacorresponding N3 interfaces facilitated via network 142. In someembodiments, user data paths for a TSN may be provided via UPF 130. TheUPF 130 is further in communication with SMF 134 via an N4 interface.

The vCU-CP 112 is in communication with each vDU 116(1)-116(2) viacorresponding F1-C interfaces and each vCU-UP 114(1)-114(2) viacorresponding E1 interfaces to facilitate control plane communicationsamong the components of the vRAN 110. The vCU-CP 112 is further incommunication AMF 132 via an N2 interface. The AMF 132 is further incommunication with SMF 134 via an N11 interface.

Various communications/operations between AMF 132 and UDM 136, PCF 138,and CHF 140 may be facilitated via 3GPP Service-Based Interfaces (SBIs).In general, an SBI represents an interface for providing/exposingvarious services among network elements/functions of communicationsystem 100. SBIs for various elements of system 100 include an Namfinterface for AMF 132, an Nsmf interface for SMF 134, an Nudm interfacefor UDM 136, an Npcf interface for PCF 138, and an Nchf interface forCHF 140. Thus, AMF 132 can interface directly with each of UDM 136, PCF138, and CHF 140 and also SMF 134 can interface directly with each ofUDM 136, PCF 138, and CHF 140. In some embodiments, for example if theinterface between AMF 132 and CHF 140 is down, AMF 132 cancommunicate/interact with CHF 140 via SMF 134.

The vCU-CP 112 operates to control the vDUs 116(1)-116(2) and thevCU-UPs 114(1)-114(2). The vCU-CP 112 and vCU-UPs 114(1)-114(2) mayprovide upper level operations of a radio signal processing stack, suchas Packet Data Convergence Protocol (PDCP) functions and radio resourcecontrol, among others. vDUs 116(1)-116(2) may provide lower leveloperations of the radio signal processing stack, such as Radio LinkControl (RLC), Medium Access Control (MAC), and physical (PHY) layeroperations, among others. The split of operations of a radio signalprocessing stack among vDUs 116(1)-116(2) and vCU-UPs 114(1)-114(2) canbe varied depending on implementation and/or configuration of vRAN 110.Antenna assemblies 118(1)-118(2) include hardware and/or software toperform baseband signal processing (such as modulation/demodulation) aswell as hardware (e.g., transmitters and receivers) for signaltransmission and signal reception via antenna assemblies 118(1)-118(2).

The UPF 130 may operate as a Virtual Network Function (VNF) to providepacket routing and forwarding operations for user data traffic and mayalso perform a variety of functions such as packet inspection, trafficoptimization, Quality of Service (QoS), billing, policy enforcement anduser data traffic, and billing operations (e.g., accounting, etc.) forUE 102(1)-102(2) sessions. Typically, the AMF 132 provides accessauthentication services, authorization services, and mobility managementcontrol. Typically, the SMF 134 is responsible for session managementwith individual functions being supported on a per session basis andalso for selection and control of a UPF (e.g., UPF 130) for datatransfer. Typically, the UDM 136 stores subscription data forsubscribers (e.g., UEs 122(1)-122(2)) and the PCF 138 stores policy datafor system 100. Typically, the CHF 140 provides charging services for UEsessions.

UEs 122(1)-122(2) may include Time Sensitive applications operatingthereon for which a TSN is required. In various embodiments, UEs122(1)-122(2) may be associated with any user, subscriber, employee,client, customer, electronic device, etc. wishing to initiate a flow insystem 100. The terms ‘UE device’, ‘UE’, ‘subscriber’, ‘UE/subscriber’,‘mobile device’, ‘user’, and variations thereof are inclusive of UEsused to initiate a communication, such as a computer, an electronicdevice such as a parking meter, vending machine, industrial device,automation device, enterprise device, appliance, Internet of Things(IoT) device, etc., a personal digital assistant (PDA), a laptop orelectronic notebook, a cellular telephone, an iPhone™, iPad™, a GoogleDroid™ phone, an IP phone, wearable electronic device or any otherdevice, component, element, or object capable of initiating voice,audio, video, media, or data exchanges within system 100. UEs discussedherein may also be inclusive of a suitable interface to a human usersuch as a microphone, a display, a keyboard, or other terminalequipment. UEs discussed herein may also be any device that seeks toinitiate a communication on behalf of another entity or element such asa program, a database, or any other component, device, element, orobject capable of initiating an exchange within system 100. It is to beunderstood that any number of UEs may be present in system 100.

Through operations discussed herein, system 100 provides for the abilityto optimize the data path for TSN sessions of UEs 122(1)-122(2) toreduce latency and jitter of TSN communications. In order to achieve theoptimizations, the signaling from the PCF 138 via the AMF 132 isenhanced to localize all data traffic for a certain TSN (e.g., TSN 120)onto a certain vCU-UP (e.g., vCU-UP 114(1)). This allows user datatraffic within TSN 120 to transit only through the particular vCU-UPinstead of forwarding it to the UPF 130. Thus, a TSN bridge isfacilitated by the particular vCU-UP to localize the user data trafficwithin vRAN 110. A TSN bridge is a Layer-2 Ethernet bridge that may becharacterized as a local connection provided by the vCU-UP to facilitaterouting of data traffic to/from multiple UE belonging to a TSN to one ormore other UE belonging to the same TSN bridge.

For cases, in which a TSN may be spread across multiple vCU-UPs, themechanism of localizing user data traffic within vRAN 110 is not used,rather a mechanism is provided to promote the TSN bridge for user datatraffic at UPF 130.

For implementing techniques described herein, the PCF 138, UDM 136, andAMF 132 are configured with correlation to various TSN 120 capabilities(e.g., TSN policies, TSN requirements, TSN endpoint customers (e.g., UEs122(1)-122(2)), etc.). PCF 138 is enhanced to store a TSN policy orrequirements for TSN 120 and UDM 136 is enhanced to store subscriberdata that indicates whether a given UE is a TSN endpoint customer and aTSN group identifier parameter “TSN-Group-ID”, which is an identifiershared by all subscribers belonging to a same TSN group. In variousembodiments, a TSN policy or requirements may include UE policyentitlements, authorization such as Layer-2 (e.g., VLAN, broadcast,default gateway, etc.), Service Area Restrictions (SARs), among others.A SAR is a policy parameter in PCF 138 which restricts whether a TSNbridge can be allowed/restricted in a specific vCU-UP or group ofvCU-UP. In at least one embodiment, SARs can be defined based ongeographical longitude-latitude for vCU-UPs. For embodiments herein,time-based billing for TSN sessions, also referred to herein as TSN PDUsessions, may be facilitated via CHF 140.

In at least one embodiment, subscriber data stored within UDM 136 can beenhanced to indicate that a given UE is a TSN endpoint customer bypresetting a parameter referred to herein as a “TSN-Localization”parameter to a Boolean value, such as TRUE (e.g.,TSN-Localization=TRUE), to indicate that the UE is a TSN endpointcustomer. Setting the TSN-Localization parameter to FALSE can be used toindicate that a given UE is not a TSN endpoint customer. As noted above,subscriber data for the UE also includes the TSN-Group-ID parameteridentifying the TSN group to which the UE belongs. In some embodiments,Customer Experience/Services may be used to automate the configurationof PCF 138 and UDM 136 with TSN capabilities.

Multiple TSNs may be configured within system 100. Additionally, in someembodiments, techniques provided herein may provide for the ability toidentify a full-distance scalar function, which includes thegeo-location of each UE, vCU-UP, and latency. In such embodiments, theTSN bridge may be set-up based on optimization parameters and preventpolarization. A mapping of all served vCU-UP can be provided so thateach TSN can be homed into a certain CU-UP for the optimal UP given theTSN latency constraints.

Given that there are stringent requirements that need to be assumed forTSN implementations, as well as subsequent routing steps (e.g., hops) tocontain delay and jitter for packets for Time Sensitive applications,provided herein are techniques which take into account TSN requirementsin the context of a vRAN. Techniques herein provide a system and methodto optimize the vRAN architecture to serve a TSN, first by selectingappropriate vRAN or UPF nodes, and second by performing local diversionof TSN traffic within the vRAN to allow an optimal low-latency path forTSN sessions.

FIGS. 2A-2B are block diagrams depicting optimized data paths for thevRAN 110 of FIG. 1 for various example scenarios, according to anexample embodiment. Reference to FIG. 1 is made in connection with thedescription of FIGS. 2A-2B.

FIG. 2A illustrates an example scenario 200 in which UE 122(1) and UE122(2) are in communication with distinct vDUs, for example, UE 122(1)is in communication with vDU 116(1) (via antenna assembly 118(1)) and UE122(2) is in communication with vDU 116(2) (via antenna assembly 118(2).

As illustrated in FIG. 2A, the solution herein may provide an optimizeddata path 210 for TSN 120 for communications between UE 122(1) and UE122(2) in which the optimized data path 210 can be localized within thevRAN 110. More specifically, a TSN bridge 212 is facilitated at vCU-UP114(1) such that data traffic for TSN 120 flows only locally through thevCU-UP 114(1) for optimized data path 210 instead of flowing through theUPF 130, as illustrated by a current data path 220.

FIG. 2B illustrates an example scenario 200′ in which UE 122(1) and UE122(2) are in communication with a common vDU, for example, vDU 116(1).

As illustrated in FIG. 2B, the solution herein may provide an optimizeddata path 230 for TSN 120 for communications between UE 122(1) and UE122(2) in which the optimized data path 230 can be localized within thevRAN 110. More specifically, a TSN bridge 232 is facilitated at vCU-UP114(1) such that data traffic for TSN 120 flows only locally through thevCU-UP 114(1) for optimized data path 230 instead of flowing through theUPF 130, as illustrated by a current data path 240.

Referring to FIG. 3, FIG. 3 is a message sequence diagram 300illustrating a call flow for facilitating a TSN bridge within vRAN 110to provide an optimized data path localized within the vRAN 110,according to an example embodiment. FIG. 3 includes UE 122(1), vDU116(1), vCU-CP 112, vCU-UP 114(1), AMF 132, UDM 136, and PCF 138. ForFIG. 3, the call flow generally illustrates that AMF 132 usesinformation received from the PCF 138 to localize a session for UE122(1) on a particular vCU-UP, for example, vCU-UP 114(1). The call flowis an extension of 3GPP Technical Specification (TS) 38.401, Section8.9.1.

At 301, a Radio Resource Control (RRC) connection request and setup areperformed between UE 122(1) and vCU-CP 112 as per 3GPP TS 38.401,Section 8.9.1. The connection request may include an attach type for UE122(1) of Layer-2 PDU or PDU unstructured (e.g., non-IP). At 302, aninitial UE message is sent from vCU-CP 112 to AMF 132 for the UE 122(1)session. The AMF 132 identifies the UE 122(1) attach type via theexchange at 302.

At 303, AMF 132 queries UDM 136 to retrieve subscriber data for the UE122(1) and identify whether the UE 122(1) session is a TSN candidate(e.g., can be localized). The AMF 132 determines whether a data sessionfor the UE at SMF 134/UPF 130 should be skipped based on subscriber data(e.g., preset in the UDM 136 as TSN endpoint customer, for example,TSN-Localization=TRUE) stored by UDM 136 for UE 122(1).

Determining that the UE 122(1) session is a TSN candidate for vRAN 110localization forces AMF 132 to determine, at 304, (e.g. using a TSNlocalization procedure configured for control logic of AMF 132) that itis to query PCF 138 based on the UE profile/subscriber data identifyingthe UE as a TSN candidate that was received from UDM 136.

At 305-307, an exchange is performed between AMF 132 and PCF 138 usingTSN specific parameters in order for AMF 132 to determine the TSN policyfor TSN 120. For example, at 305, AMF sends (via the Npcf interface) anNpcf_AMPolicyControlCreate Request (Req) message to PCF 138. The messageincludes various parameters associated with UE 122(1) including theTSN-Group-ID for the TSN group of which UE 122(1) is a member and thecurrent vCU-UP (e.g., vCU-UP 114(1)) allocated to handle data trafficfor the UE 122(1).

At 306, PCF 138 determines whether localization for UE 122(1) ispossible. The TSN-Group-ID received from AMF 132 can help PCF 138determine whether current members of the TSN group can be localized and,if so, at what vCU-UP. Various outcomes are possible based on thedetermination made by PCF 138 at 306.

For example, based on a determination at 306 by PCF 138 that this is thefirst TSN session for the TSN group (e.g., no other UE of the groupcurrently have TSN PDU sessions (data traffic) associated with the TSN),PCF 138 can select the vCU-UP with the least load in the serving area(e.g., geographical location) of the UE 122(1) to which to home(localize) data traffic for the TSN 120. The PCF 138 updates itsdatabase (e.g., the TSN policy for TSN 120) to identify the selectedvCU-UP for the TSN 120. In one embodiment, the PCF 138 could use thecurrent vCU-UP as supplied in the Npcf_AMPolicyControlCreate Requestmessage to update its database for the TSN 120.

For this example, PCF 138 can send an Npcf_AMPolicyControlCreateResponse (Resp) message at 307 that includes fields including a vCU-UPidentifier, such as the IP address or a node identifier (node_id) forthe selected vCU-UP at which the TSN group is to be homed, a L2 PDUidentifier for the TSN bridge to be set-up, the TSN-Group-ID, SARs forthe TSN 120, and also the parameter TSN-Localization=TRUE. In at leastone embodiment, the L2 PDU identifier is a unique numeric value that canbe assigned by the network (e.g., PCF 138) or selected by UE 122(1). Invarious embodiments, the L2 PDU identifier may be a Virtual Local AreaNetwork (VLAN) address or a MAC address.

In another example, based on a determination by PCF 138 that this is notthe first TSN session for the TSN group, PCF 138 can determine at 306whether the current vCU-UP at which other members of the group (e.g.,other UE) are homed is within the same serving area as UE 122(1). Basedon a determination that the current vCU-UP for the TSN group is withinthe same serving area as UE 122(1), PCF 138 can send anNpcf_AMPolicyControlCreate Response (Resp) message at 307 that includesfields including the currently homed vCU-UP for the TSN group, the L2PDU identifier for each TSN bridge set-up, the TSN-Group-ID, SARs, andthe parameter TSN-Localization=TRUE for UE 122(1).

In yet another example, based on a determination by PCF 138 that thecurrent vCU-UP for the TSN group is not within the same serving area asUE 122(1), PCF 138 can determine that the localization procedure is tobe skipped because TSN localization for UE 122(1) would cause the TSNgroup to be spread across more than one vCU-UP. Based on such adetermination that localization would cause the TSN group to be spreadacross more than one vCU-UP, PCF 138 can determine that a full datasession is to be established for the UE via SMF 134 and homed on asingle UPF (e.g., UPF 130).

For the embodiment of FIG. 3, it is assumed that this is the first TSNsession for the TSN group to which UE 122(1) belongs in which case PCF138 selects vCU-UP 114(1) to which to home the TSN group and sends anNpcf_AMPolicyControlCreate Response message at 307 that includes thevCU-UP identifier for the selected vCU-UP 114(1), a L2 PDU identifierfor the TSN bridge to be set-up for UE 122(1), the TSN-Group-ID for theTSN group of which UE 122(1) is a member, SARs for the TSN 120, and alsothe parameter TSN-Localization=TRUE for UE 122(1).

At 308, AMF 132 determines based on the PCF 138 response (e.g., SARs)and session criteria for UE 122(1) (e.g., UE attach type PDN (PDU)unstructured or L2 PDU and TSN-Localization=TRUE) that it is to skipdata session creation for UE 122(1) at SMF 134. At 309, AMF 132 augmentsthe UE response to vCU-CP 112 to indicate a localized TSN session is tobe used for UE 122(1) data traffic. The response includes the L2 PDUidentifier for the TSN bridge that is to be set-up for localizing the UE122(1) data traffic within vRAN 110.

In some embodiments, if there is no current home for the TSN group towhich UE 122(1) belongs because this is the first TSN session for theTSN group, the AMF 132 can use the currently allocated vCU-UP 114(1)(e.g., as identified by PCF 138 in the response message at 307) as theTSN home vCU-UP for handling the data traffic for the UE 122(1) TSNsession. Based on the response received from AMF 132 at 309, vCU-CP 112performs, at 310, TSN PDU session establishment for UE 112(1) at vCU-UP114(1) using the L2 PDU identifier for the TSN bridge received from AMF132. Other information may be included in the signaling from vCU-CP 112to vCU-UP 114(1) to establish billing for the UE TSN session, asdiscussed in further detail below.

In still some embodiments, if the vCU-UP identified by the AMF 132 inthe response at 307 for the TSN home is different than the currentlyallocated vCU-UP for the UE 122(1) session based on TSN locationinformation (e.g., either because the TSN group is homed to a differentvCU-UP or another vCU-UP has a lower load than the currently allocatedvCU-UP), AMF 132 can trigger a vCU-UP change for the TSN session for UE122(1) at 311. Based on the trigger at 3110, vCU-CP 112 initiates, at312, a relocation of the currently allocated vCU-UP for the UE 122(1)session to vCU-UP 114(1). As shown at 313, subsequent data traffic forUE 122(1) flows only locally through the vCU-UP 114(1) and not via UPF130.

Referring to FIG. 4, FIG. 4 is a message sequence diagram 400illustrating a call flow for facilitating usage reporting for UE datatraffic associated with a TSN, according to an example embodiment. FIG.4 includes UE 122(1), vCU-UP 114(1), vCU-CP 112, AMF 132, SMF 134 andCHF 140. For FIG. 4, the call flow generally illustrates that usagereports for UE 122(1) can be sent from the vRAN 110 to AMF 132, whichcan either forward them to CHF 140 via the Namf/Nchf SBI for cases inwhich data traffic for the UE is localized within the vRAN 110, or AMF132 can forward them to SMF 134 that can then forward them to CHF 140via the Nsmf/Nchf SBI for cases in which a data session for the UE iscreated at UPF 130 or for cases in which the Namf/Nchf SBI between AMF132 and CHF 140 has failed. Usage reporting can be provided for each TSNPDU session per UE for a TSN.

Thus, usage reporting can go from AMF 132 to CHF 140, which isbeneficial as when the UE disconnects, the last usage report is onlyavailable on the AMF 132.

As illustrated at 401, AMF 132 determines that the PDU session for UE122(1) can be localized within vRAN 110 on vCU-UP 114(1) based on theUDM response including an indication that TSN-Localization=TRUE for UE122(1) and the policy information returned by PCF 138 (e.g., asdiscussed above).

Based on the determination at 401, AMF 132 sends, at 402, a trigger tovCU-CP 112 to establish a localized TSN path (bridge) for UE 122(1) forTSN 120 within the vRAN 110 at vCU-UP 114(1) in which the triggerincludes a usage reporting rule or policy for the UE 122(1) TSN session.In at least one embodiment, the usage reporting rule may include timeinformation (e.g., for a periodic timer) and/or mobility eventinformation that may indicate when a usage report is to be sent for theUE 122(1) TSN PDU session. At 403, vCU-CP 112 performs TSN sessionestablishment for UE 122(1) (not shown in FIG. 4) at vCU-UP 114(1) thatinvolves usage report installation for the UE TSN PDU session.

After some time, it is assumed that data traffic for the TSN 120 isreceived/handled by vCU-UP 114(1) at 404 for the UE 122(1) TSN PDUsession. After a period of time (e.g., based on policy, etc.), aperiodic timer configured for vCU-UP 114(1) triggers at 405 to reportusage for the UE 122(1) TSN session and a session report is sent at 406from vCU-UP 114(1) to vCU-CP 112. At 407, vCU-CP 112 determines based onthe reporting policy time and/or mobility event to report usage for theUE 122(1) TSN session. Based on the determination and the session reportreceived from vCU-UP 114(1) at 406, vCU-CP 112 sends a usage report at408. In at least one embodiment, a usage report may include a number ofbytes of downlink data delivered to the UE and/or the number of bytes ofuplink data received from the UE. Upon receiving the vRAN usage report,AMF 132 sends, at 409, the vRAN usage report as a TSN PDU usage reportdirectly to CHF 140 via the Namf/Nchf SBI.

As shown at 410, for a case in which a TSN PDU session for UE 122(1) iswith SMF 134 (e.g., as is applicable for cases in which the TSN bridgefor UE 122(1) is set-up in the SMF 134/UPF 130) or in which the SBIbetween AMF 132 and CHF 140 is down, AMF 132 can send vRAN usage reportsto SMF 134 at 411 and SMF 134 can send TSN PDU usage reports to CHF 140at 412.

Operations that may be associated with a UE 122(1) disconnect or a PDUsession disconnect are illustrated at 420. Based on a UE 122(1)disconnect or PDU disconnect for the UE 122(1) TSN PDU session, AMF 132sends an N2 release message to vCU-CP 112 at 421, which triggers vCU-CP112 to communicate a session release for UE 122(1) to vCU-UP 114(1) at422. Based on receiving the session release, vCU-UP 114(1) sends tovCU-CP 112, at 423, and acknowledgment (ACK) of the release and a finalusage report for the UE 122(1) TSN PDU session. At 424, vCU-CP 112forwards the ACK and the final usage report to AMF 132.

As shown at 430, for a case in which the TSN PDU session for UE 122(1)data traffic is localized within the vRAN 110 (e.g., without the SMF134/UPF 130), AMF 132 communicates to CHF 140 to close thebilling/charging record for UE 122(1) including a TSN PDU usage report.In other cases in which a TSN PDU session for UE 122(1) is with SMF 134or in which the SBI between AMF 132 and CHF 140 is down (not shown inFIG. 4), AMF 132 can communicate to SMF 134 to close the charging recordfor UE 122(1) including a TSN PDU usage report, which SMF 134 canforward to CHF 140.

Referring to FIG. 5, FIG. 5 is a flow chart illustrating a method 500according to an example embodiment. The method 500 may be performed, atleast in part, by an AMF that is in communication with an SMF, UDM, PCF,CHF, and vCU-CP of a vRAN (e.g., as illustrated in FIGS. 1 and 3-4).

At 502, the AMF determines that a UE is associated with a time sensitivenetwork. For example, the AMF can query the UDM to determine subscriberinformation associated with the UE that indicates TSN-Localization=TRUEand a TSN-Group-ID for the UE.

At 504, the AMF determines whether data traffic (e.g., a TSN PDUsession) for the UE can be localized at one centralized unit user planecomponent of the vRAN (e.g., one vCU-UP). The determination at 504 isbased on an exchange with the PCF in which the PCF returns information(e.g., the TSN-Localization parameter, the TSN-Group-ID parameter, a L2PDU identifier for a TSN bridge to be set-up, a vCU-UP IP address ornode_id, SARs, etc.) to the AMF that indicates whether the data trafficcan be localized at one centralized unit user plane component or not.

Based on a determination that the data traffic for the UE can belocalized to one centralized unit user plane component within the vRAN,the method can include, at 506, the AMF localizing the data traffic forthe UE at one centralized unit user plane component within the vRAN forthe TSN. The localizing at 506 can include creating a TSN bridge (viathe vCU-CP) at the centralized unit user plane component for localizingthe data traffic (e.g., the TSN PDU session) for the UE within the vRAN.

Returning to 504, based on a determination that the data traffic for theUE cannot be localized to one centralized unit user plane componentwithin the vRAN, the method can include, at 508, creating a data sessionfor the UE at a user plane function outside the vRAN. The session can becreated via the SMF and a user plane function selected by the SMF.

At 510, the method can include the providing usage report(s) for thedata traffic to the CHF via a service-based interface. The usagereport(s) can be provided to the CHF using different techniques. Forcases in which the data traffic for the UE is localized within the vRAN,the AMF receive usage reports from the vRAN (via the vCU-CP) and cansend the usage reports directly to the CHF via the Namf/Nchf SBI. Forcases in which a data session is created for the UE via the SMF/userplane function or in which the interface between the AMF and the CHF isdown, the AMF can receive usage reports from the vRAN (via the vCU-CP)and can send the usage reports to the SMF, which can then send thereports to the CHF. For multiple UEs belonging to a TSN, usage reportscan be provided to the CHF for each TSN PDU session per UE.

In summary, a system and method are provided to optimize the vRANarchitecture to serve a TSN, first by selecting appropriate vRAN or UPFnodes, and second by performing local diversion of TSN traffic withinthe vRAN to allow an optimal low-latency path for TSN sessions.

FIG. 6 illustrates a hardware block diagram of a computing device 600that may perform the functions of any of nodes, functions, elements,etc. of system 100, referred to herein in connection with FIGS. 1-5(e.g., AMF 132, UDM 136, PCF 138, vCU-CP 112, etc.). It should beappreciated that FIG. 6 provides only an illustration of one embodimentand does not imply any limitations with regard to the environments inwhich different embodiments may be implemented. Many modifications tothe depicted environment may be made.

As depicted, the device 600 includes a bus 612, which providescommunications between computer processor(s) 614, memory 616, persistentstorage 618, communications unit 620, and input/output (I/O)interface(s) 522. Bus 612 can be implemented with any architecturedesigned for passing data and/or control information between processors(such as microprocessors, communications and network processors, etc.),system memory, peripheral devices, and any other hardware componentswithin a system. For example, bus 612 can be implemented with one ormore buses.

Memory 616 and persistent storage 618 are computer readable storagemedia. In the depicted embodiment, memory 616 includes random accessmemory (RAM) 624 and cache memory 626. In general, memory 616 caninclude any suitable volatile or non-volatile computer readable storagemedia. Instructions for control logic 617 (e.g., for an AMF, UDM, PCF,vCU-CP, etc.) may be stored in memory 616 or persistent memory 518 forexecution by processor(s) 614. When the processor(s) 614 execute thecontrol logic 617, the processor(s) 614 are caused to perform theoperations (e.g., for an AMF, UDM, PCF, vCU-CP, etc.) described above inconnection with FIGS. 1-5.

One or more programs may be stored in persistent storage 618 forexecution by one or more of the respective computer processors 614 viaone or more memories of memory 616. The persistent storage 618 may be amagnetic hard disk drive, a solid state hard drive, a semiconductorstorage device, read-only memory (ROM), erasable programmable read-onlymemory (EPROM), flash memory, or any other computer readable storagemedia that is capable of storing program instructions or digitalinformation.

The media used by persistent storage 618 may also be removable. Forexample, a removable hard drive may be used for persistent storage 618.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage618.

Communications unit 620, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 620 includes one or more network interface cards.Communications unit 620 may provide communications through the use ofeither or both physical and wireless communications links.

I/O interface(s) 622 allows for input and output of data with otherdevices that may be connected to computer device 600. For example, I/Ointerface(s) 622 may provide a connection to external devices 628 suchas a keyboard, keypad, a touch screen, and/or some other suitable inputdevice. External devices 628 can also include portable computer readablestorage media such as database systems, thumb drives, portable opticalor magnetic disks, and memory cards.

Software and data used to practice embodiments can be stored on suchportable computer readable storage media and can be loaded ontopersistent storage 618 via I/O interface(s) 622. I/O interface(s) 622may also connect to a display 630. Display 630 provides a mechanism todisplay data to a user and may be, for example, a computer monitor.

In one form, a computer-implemented method is provided and may includedetermining that a user equipment (UE) is associated with a timesensitive network; and localizing data traffic for the UE within avirtualized radio access network based on determining that the datatraffic for the UE can be localized at one centralized user planecomponent of the virtualized radio access network for the time sensitivenetwork. The virtualized radio access network may include a plurality ofdistributed user plane components and a plurality of centralized userplane components. The data traffic can be Layer-2 (L2) data traffic orunstructured data traffic. The determining and the localizing can beperformed, at least in part, by an access and mobility managementfunction.

In some cases, the computer-implemented method may include creating adata session for the UE on a user plane function outside the virtualizedradio access network based on determining that the data traffic for theUE cannot be localized at one centralized user plane component of thevirtualized radio access network for the time sensitive network.

For the computer-implemented method, determining that the data trafficfor the UE can be localized at one centralized user plane component ofthe virtualized radio access network for the time sensitive network mayinclude identifying that the UE is a candidate for having the datatraffic localized within the virtualized radio access network based onsubscriber information stored for the UE at a unified data managementnetwork element. The subscriber information may include a groupidentifier for a group comprising a plurality of UE that are associatedwith the time sensitive network, wherein the UE is a member of thegroup.

Further for the computer-implemented method, determining that the datatraffic for the UE can be localized at one centralized user planecomponent of the virtualized radio access network for the time sensitivenetwork may further include: determining whether other UE of the groupcurrently have data traffic associated with the time sensitive network;based on determining that no other UE of the group currently has datatraffic associated with the time sensitive network, selecting acentralized user plane component of the virtualized radio access networkto handle the data traffic for the UE for the time sensitive network;based on determining that other UE of the group currently have datatraffic that is handled at a particular centralized user plane componentof the virtualized radio access network, determining whether theparticular centralized user plane component is within a serving area ofthe UE; based on determining that the particular centralized user planecomponent is within the serving area of the UE, localizing the datatraffic for the UE to the particular centralized user plane component;and based on determining that the particular centralized user planecomponent is not within the serving area of the UE, creating a datasession for the UE at a user plane function outside the virtualizedradio access network.

Further for the computer-implemented method, based on determining thatno other UE of the group currently has data traffic associated with thetime sensitive network, selecting the centralized user plane componentof the virtualized radio access network to handle the data traffic forthe UE comprises selecting the centralized user plane component having alowest load within a serving area of the UE.

The computer-implemented method may further include providing, for aplurality of UE that are associated with the time sensitive network, atleast one usage report associated with data traffic for each timesensitive network packet data unit session per UE of the plurality of UEto a charging function. Further for the computer-implemented method, theat least one usage report can be provided from an access and mobilitymanagement function to the charging function via a service-basedinterface. Further for the computer-implemented method, the at least oneusage report can be provided from an access and mobility managementfunction to a session management function when a data session for atleast one UE is created on a user plane function outside the virtualizedradio access network in which the computer-implemented method mayfurther include the session management function providing the usagereport to the charging function via a service-based interface.

In another form, one or more non-transitory computer readable storagemedia encoded with instructions may be provided that, when executed by aprocessor, cause the processor to perform operations, comprisingdetermining that the data traffic for the UE can be localized at onecentralized user plane component of the virtualized radio access networkfor the time sensitive network may include identifying that the UE is acandidate for having the data traffic localized within the virtualizedradio access network based on subscriber information stored for the UEat a unified data management network element.

In still another form, a system may be provided that may include atleast one memory element for storing data; and at least one processorfor executing instructions associated with the data, wherein executingthe instructions causes the system to perform operations, comprising:determining that a user equipment (UE) is associated with a timesensitive network; and localizing data traffic for the UE within avirtualized radio access network based on determining that the datatraffic for the UE can be localized at one centralized user planecomponent of the virtualized radio access network for the time sensitivenetwork

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment. However, itshould be appreciated that any particular program nomenclature herein isused merely for convenience, and thus the embodiments should not belimited to use solely in any specific application identified and/orimplied by such nomenclature.

Data relating to operations described herein may be stored within anyconventional or other data structures (e.g., files, arrays, lists,stacks, queues, records, etc.) and may be stored in any desired storageunit (e.g., database, data or other repositories, queue, etc.). The datatransmitted between entities may include any desired format andarrangement, and may include any quantity of any types of fields of anysize to store the data. The definition and data model for any datasetsmay indicate the overall structure in any desired fashion (e.g.,computer-related languages, graphical representation, listing, etc.).

The present embodiments may employ any number of any type of userinterface (e.g., Graphical User Interface (GUI), command-line, prompt,etc.) for obtaining or providing information (e.g., data relating toscraping network sites), where the interface may include any informationarranged in any fashion. The interface may include any number of anytypes of input or actuation mechanisms (e.g., buttons, icons, fields,boxes, links, etc.) disposed at any locations to enter/displayinformation and initiate desired actions via any suitable input devices(e.g., mouse, keyboard, etc.). The interface screens may include anysuitable actuators (e.g., links, tabs, etc.) to navigate between thescreens in any fashion.

The environment of the present embodiments may include any number ofcomputer or other processing systems (e.g., client or end-user systems,server systems, etc.) and databases or other repositories arranged inany desired fashion, where the present embodiments may be applied to anydesired type of computing environment (e.g., cloud computing,client-server, network computing, mainframe, stand-alone systems, etc.).The computer or other processing systems employed by the presentembodiments may be implemented by any number of any personal or othertype of computer or processing system (e.g., desktop, laptop, PDA,mobile devices, etc.), and may include any commercially availableoperating system and any combination of commercially available andcustom software (e.g., machine learning software, etc.). These systemsmay include any types of monitors and input devices (e.g., keyboard,mouse, voice recognition, etc.) to enter and/or view information.

It is to be understood that the software of the present embodiments maybe implemented in any desired computer language and could be developedby one of ordinary skill in the computer arts based on the functionaldescriptions contained in the specification and flow charts illustratedin the drawings. Further, any references herein of software performingvarious functions generally refer to computer systems or processorsperforming those functions under software control. The computer systemsof the present embodiments may alternatively be implemented by any typeof hardware and/or other processing circuitry.

The various functions of the computer or other processing systems may bedistributed in any manner among any number of software and/or hardwaremodules or units, processing or computer systems and/or circuitry, wherethe computer or processing systems may be disposed locally or remotelyof each other and communicate via any suitable communications medium(e.g., Local Area Network (LAN), Wide Area Network (WAN), Intranet,Internet, hardwire, modem connection, wireless, etc.). For example, thefunctions of the present embodiments may be distributed in any manneramong the various end-user/client and server systems, and/or any otherintermediary processing devices. The software and/or algorithmsdescribed above and illustrated in the flow charts may be modified inany manner that accomplishes the functions described herein. Inaddition, the functions in the flow charts or description may beperformed in any order that accomplishes a desired operation.

The software of the present embodiments may be available on anon-transitory computer useable medium, non-transitory computer readablestorage medium, or the like (e.g., magnetic or optical mediums,magneto-optic mediums, floppy diskettes, CD-ROM, DVD, memory devices,etc.) of a stationary or portable program product apparatus or devicefor use with stand-alone systems or systems connected by a network orother communications medium.

The system may be implemented by any number of any type ofcommunications network (e.g., LAN, WAN, Internet, Intranet, VirtualPrivate Network (VPN), etc.). The computer or other processing systemsof the present embodiments may include any conventional or othercommunications devices to communicate over the network via anyconventional or other protocols. The computer or other processingsystems may utilize any type of connection (e.g., wired, wireless, etc.)for access to the network. Local communication media may be implementedby any suitable communication media (e.g., LAN, hardwire, wireless link,Intranet, etc.).

The system may employ any number of any conventional or other databases,data stores or storage structures (e.g., files, databases, datastructures, data or other repositories, etc.) to store information(e.g., data relating to contact center interaction routing). Thedatabase system may be implemented by any number of any conventional orother databases, data stores or storage structures (e.g., files,databases, data structures, data or other repositories, etc.) to storeinformation (e.g., data relating to contact center interaction routing).The database system may be included within or coupled to the serverand/or client systems. The database systems and/or storage structuresmay be remote from or local to the computer or other processing systems,and may store any desired data (e.g., data relating to contact centerinteraction routing).

The present embodiments may employ any number of any type of userinterface (e.g., Graphical User Interface (GUI), command-line, prompt,etc.) for obtaining or providing information (e.g., data relating toproviding enhanced delivery options), where the interface may includeany information arranged in any fashion. The interface may include anynumber of any types of input or actuation mechanisms (e.g., buttons,icons, fields, boxes, links, etc.) disposed at any locations toenter/display information and initiate desired actions via any suitableinput devices (e.g., mouse, keyboard, etc.). The interface screens mayinclude any suitable actuators (e.g., links, tabs, etc.) to navigatebetween the screens in any fashion.

The embodiments presented may be in various forms, such as a system, amethod, and/or a computer program product at any possible technicaldetail level of integration. The computer program product may include acomputer readable storage medium (or media) having computer readableprogram instructions thereon for causing a processor to carry outaspects of presented herein.

The computer readable storage medium, which can be inclusive of anon-transitory computer readable storage medium, can be a tangibledevice that can retain and store instructions for use by an instructionexecution device. The computer readable storage medium may be, forexample, but is not limited to, an electronic storage device, a magneticstorage device, an optical storage device, an electromagnetic storagedevice, a semiconductor storage device, or any suitable combination ofthe foregoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions, which can be inclusive ofnon-transitory computer readable program instructions, for carrying outoperations of the present embodiments may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a LAN or a WAN, or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider). In some embodiments,electronic circuitry including, for example, programmable logiccircuitry, field-programmable gate arrays (FPGA), or programmable logicarrays (PLA) may execute the computer readable program instructions byutilizing state information of the computer readable programinstructions to personalize the electronic circuitry, in order toperform aspects presented herein.

Aspects of the present embodiments are described herein with referenceto flow chart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to the embodiments.It will be understood that each block of the flow chart illustrationsand/or block diagrams, and combinations of blocks in the flow chartillustrations and/or block diagrams, can be implemented by computerreadable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flow chart(s) and block diagram(s) in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments. In this regard, each block in the flowchart or blockdiagrams may represent a module, segment, or portion of instructions,which comprises one or more executable instructions for implementing thespecified logical function(s). In some alternative implementations, thefunctions noted in the blocks may occur out of the order noted in thefigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. It will also be noted that each block of the block diagramsand/or flowchart illustration, and combinations of blocks in the blockdiagrams and/or flowchart illustration, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts or carry out combinations of special purpose hardware and computerinstructions.

The descriptions of the various embodiments have been presented forpurposes of illustration, but are not intended to be exhaustive orlimited to the embodiments disclosed. Many modifications and variationswill be apparent to those of ordinary skill in the art without departingfrom the scope and spirit of the described embodiments. The terminologyused herein was chosen to best explain the principles of theembodiments, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

What is claimed is:
 1. A method comprising: determining that a userequipment (UE) is associated with a time sensitive network; andlocalizing data traffic for the UE within a virtualized radio accessnetwork based on determining that the data traffic for the UE can belocalized at one centralized user plane component of the virtualizedradio access network for the time sensitive network.
 2. The method ofclaim 1, wherein the virtualized radio access network comprises aplurality of distributed user plane components and a plurality ofcentralized user plane components.
 3. The method of claim 1, wherein thedata traffic is Layer-2 data traffic or unstructured data traffic. 4.The method of claim 1, wherein the determining and the localizing areperformed, at least in part, by an access and mobility managementfunction.
 5. The method of claim 1, further comprising: creating a datasession for the UE on a user plane function outside the virtualizedradio access network based on determining that the data traffic for theUE cannot be localized at one centralized user plane component of thevirtualized radio access network for the time sensitive network.
 6. Themethod of claim 1, wherein determining that the data traffic for the UEcan be localized at one centralized user plane component of thevirtualized radio access network for the time sensitive network furthercomprises: identifying that the UE is a candidate for having the datatraffic localized within the virtualized radio access network based onsubscriber information stored for the UE at a unified data managementnetwork element.
 7. The method of claim 6, wherein the subscriberinformation includes a group identifier for a group comprising aplurality of UE that are associated with the time sensitive network,wherein the UE is a member of the group.
 8. The method of claim 7,wherein determining that the data traffic for the UE can be localized atone centralized user plane component of the virtualized radio accessnetwork for the time sensitive network further comprises: determiningwhether other UE of the group currently have data traffic associatedwith the time sensitive network; based on determining that no other UEof the group currently has data traffic associated with the timesensitive network, selecting a centralized user plane component of thevirtualized radio access network to handle the data traffic for the UEfor the time sensitive network; based on determining that other UE ofthe group currently have data traffic that is handled at a particularcentralized user plane component of the virtualized radio accessnetwork, determining whether the particular centralized user planecomponent is within a serving area of the UE; based on determining thatthe particular centralized user plane component is within the servingarea of the UE, localizing the data traffic for the UE to the particularcentralized user plane component; and based on determining that theparticular centralized user plane component is not within the servingarea of the UE, creating a data session for the UE at a user planefunction outside the virtualized radio access network.
 9. The method ofclaim 8, wherein based on determining that no other UE of the groupcurrently has data traffic associated with the time sensitive network,selecting the centralized user plane component of the virtualized radioaccess network to handle the data traffic for the UE comprises selectingthe centralized user plane component having a lowest load within aserving area of the UE.
 10. The method of claim 1, further comprising:providing, for a plurality of UE that are associated with the timesensitive network, at least one usage report associated with datatraffic for each time sensitive network packet data unit session per UEof the plurality of UE to a charging function.
 11. The method of claim10, wherein the at least one usage report is provided from an access andmobility management function to the charging function via aservice-based interface.
 12. The method of claim 10, wherein the atleast one usage report is provided from an access and mobilitymanagement function to a session management function when a data sessionfor at least one UE is created on a user plane function outside thevirtualized radio access network, the method further comprising thesession management function providing the usage report to the chargingfunction via a service-based interface.
 13. One or more non-transitorycomputer readable storage media encoded with instructions that, whenexecuted by a processor, cause the processor to perform operations,comprising: determining that a user equipment (UE) is associated with atime sensitive network; and localizing data traffic for the UE within avirtualized radio access network based on determining that the datatraffic for the UE can be localized at one centralized user planecomponent of the virtualized radio access network for the time sensitivenetwork.
 14. The media of claim 13, wherein the data traffic is Layer-2data traffic or unstructured data traffic.
 15. The media of claim 13,wherein determining that the data traffic for the UE can be localized atone centralized user plane component of the virtualized radio accessnetwork for the time sensitive network further comprises: identifyingthat the UE is a candidate for having the data traffic localized withinthe virtualized radio access network based on subscriber informationstored for the UE at a unified data management network element, whereinthe subscriber information includes a group identifier for a groupcomprising a plurality of UE that are associated with the time sensitivenetwork, wherein the UE is a member of the group.
 16. The media of claim15, wherein determining that the data traffic for the UE can belocalized at one centralized user plane component of the virtualizedradio access network for the time sensitive network further comprises:determining whether other UE of the group currently have data trafficassociated with the time sensitive network; based on determining that noother UE of the group currently has data traffic associated with thetime sensitive network, selecting a centralized user plane component ofthe virtualized radio access network to handle the data traffic for theUE for the time sensitive network; based on determining that other UE ofthe group currently have data traffic that is handled at a particularcentralized user plane component of the virtualized radio accessnetwork, determining whether the particular centralized user planecomponent is within a serving area of the UE; based on determining thatthe particular centralized user plane component is within the servingarea of the UE, localizing the data traffic for the UE to the particularcentralized user plane component; and based on determining that theparticular centralized user plane component is not within the servingarea of the UE, creating a data session for the UE at a user planefunction outside the virtualized radio access network.
 17. The media ofclaim 13, further comprising instructions that, when executed by theprocessor, cause the processor to perform further operations,comprising: providing, for a plurality of UE that are associated withthe time sensitive network, at least one usage report associated withdata traffic for each time sensitive network packet data unit sessionper UE of the plurality of UE to a charging function.
 18. A systemcomprising: at least one memory element for storing data; and at leastone processor for executing instructions associated with the data,wherein executing the instructions causes the system to performoperations, comprising: determining that a user equipment (UE) isassociated with a time sensitive network; and localizing data trafficfor the UE within a virtualized radio access network based ondetermining that the data traffic for the UE can be localized at onecentralized user plane component of the virtualized radio access networkfor the time sensitive network.
 19. The system of claim 18, wherein thedata traffic is Layer-2 data traffic or unstructured data traffic. 20.The system of claim 18, wherein the determining and the localizing areperformed, at least in part, by an access and mobility managementfunction.